Task: Analyze Change Request

Every change requested must be analysed first in order to guarantee the verification of many topics regarding the change.

The topics that must be covered are described in the Change Analysis checklist and all of these topics should be analysed in oder to approve the implementation of a specific CR.

The result of the anaylsis must be documented inside the CR, following the proposed "CCB Analysis documentation template".

Identify if the CR is related to CAD or PD

It is important to verify if the change requested relates to CAD or PD.

eg1. If this activity is being conducted in the CAD, then all changes analysed should be related to CAD, otherwise an observation should be included in the CR stating that the CR is nor related to CAD, and then it is fowarded to PD.

eg2. If this activity is being conducted in the PD, then all changes analysed should be related to PD, otherwise an observation should be included in the CR stating that the CR is nor related to PD, and then it is fowarded to CAD.

[optional] Identify if the problem/bug is reproducible

If the CR is a bug report, then it is necessary to verify if the bug can be reproducible. If the problem is not reproducible, this has to be documented in the CCB analysis decision.

Identify all change's impacts and feasibility

This analysis has to follow the attached checklist (CR Analysis checklist) and each check have to be checked in oder to assess all impacts of the change proposed.

Negociate and Assign a person to implement the CR

The CR resolution must be assigned to some oe in the team. This person would be responsible for the implementation(realization) of this CR.

Document the CCB Analysis

The result of the anaylsis must be documented inside the CR, following the proposed "CCB Analysis documentation template".